Don't protect public files path #9457
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rachelwhitton
added
Type: Quick Fix
|
@ccharlton can you review when convenient? |
|
I have seen a good use of this pattern in the field (by a partner) where adding deeper sub-folder paths within the WP uploads folder helps in certain use cases, so I'm seeing this a bit differently. Please add the context of adding the top-level public files folder is unadvised, and subpaths are supported. That will help be clear for the more intermediate Composer setups I'm seeing in the field from a couple of WordPress projects we're attached to. Thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #9452